Fix segfault from readline()
; avoid unnecessary string copy
#1665
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I encountered a segmentation fault from reticulate's internal
readline()
function while evaluating interleaved R and Python chunks in RStudio within a Quarto document.gdb backtrace
While I'm not entirely sure this change completely resolves the segfault (as I didn’t have a reliable reproducible example beforehand), this PR represents an improvement, and I can no longer reproduce the segfault.
This PR updates reticulate's internal
readline()
to eliminate an unnecessary allocation and copy of the input instd::string()
.As far as I can tell, the reason we maintain our own
readline()
function, rather than usingbase::readline()
, is due to the limited input size in base R, which truncates input at 256 characters. In contrast, our implementation accepts up to 8192 characters (and this limit can be easily adjusted).